test/core/command-generation/registry.test.ts (1)

24-28: Add Junie behavior assertions, not only registry presence.

Lines 24-28 and Line 63 validate registration, but they don’t verify Junie-specific path/format behavior. A broken Junie adapter implementation could still pass these tests.

Suggested test additions

@@
     it('registered adapters should have working getFilePath', () => {
       const claudeAdapter = CommandAdapterRegistry.get('claude');
       const cursorAdapter = CommandAdapterRegistry.get('cursor');
       const windsurfAdapter = CommandAdapterRegistry.get('windsurf');
+      const junieAdapter = CommandAdapterRegistry.get('junie');

       expect(claudeAdapter?.getFilePath('test')).toContain('.claude');
       expect(cursorAdapter?.getFilePath('test')).toContain('.cursor');
       expect(windsurfAdapter?.getFilePath('test')).toContain('.windsurf');
+      expect(junieAdapter?.getFilePath('test')).toContain('.junie');
+      expect(junieAdapter?.getFilePath('test')).toContain('opsx-test.md');
     });
@@
       const adapters = CommandAdapterRegistry.getAll();
       for (const adapter of adapters) {
         const output = adapter.formatFile(content);
@@
       }
+
+      const junieOutput = CommandAdapterRegistry.get('junie')?.formatFile(content) ?? '';
+      expect(junieOutput).toContain('description: Test desc');
+      expect(junieOutput).toContain('Body content');
     });

Also applies to: 63-63

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@test/core/command-generation/registry.test.ts` around lines 24 - 28, The test
currently only checks registry presence for CommandAdapterRegistry.get('junie');
extend it to exercise Junie-specific behavior by calling the adapter's public
formatting/build method(s) (e.g., adapter.formatCommand(...) or
adapter.buildCommand(...) — whichever the CommandAdapter interface exposes) with
a representative input and assert the returned path/format/command matches Junie
expectations (for example specific path prefix, file extension, or command
structure) in the same test block (and similarly at the other location around
line 63); keep the existing toolId assertion and add one or two focused
assertions that validate Junie-specific output so a broken Junie adapter
implementation will fail the test.